MODE¶

virt-who has four modes how it can run:

1. one-shot mode

# virt-who -o

In this mode virt-who just sends the host to guest association to the server once and then exits.

2. interval mode

# virt-who -i INTERVAL

This is the default mode. virt-who will listen to change events (if available) or do a polling with given interval, and will send the host to guest association when it changes. The default polling interval is 3600 seconds and can be changed using "-i INTERVAL" (in seconds).

3. print mode

# virt-who -p

This mode is similar to oneshot mode but the host to guest association is not send to server, but printed to standard output instead.

3. status mode

# virt-who -s

This mode is for configuration diagnosis. The host to guest association is not compiled and is not sent to the server. When executed, it will confirm the ability to log into and retrieve data from the source for each configuration. It will also confirm the credentials and organization for each destination in the configurations. It will produce results in two ways that can be used to diagnose problems. The first is a summary:

Configuration Name: esx_config1
Source Status: success
Destination Status: success

Configuration Name: hyperv-55
Source Status: failure
Destination Status: failure

The second is a machine-readable json output (which is generated when the -j/--json option is used):

{
"configurations": [
{
"name":"esx-conf1",
"source":{
"connection":"esx_system.example.com",
"status":"success",
"last_successful_retrieve":"2020-02-28 07:25:25 UTC",
"hypervisors":20,
"guests":37
},
"destination":{
"connection":"candlepin.example.com",
"status":"success",
"last_successful_send":"2020-02-28 07:25:27 UTC",
"last_successful_send_job_status":"FINISHED"
}
},
{
"name":"hyperv-55",
"source":{
"connection":"windows10-3.company.com",
"status":"failure",
"message":"Unable to connect to server: invalid credentials",
"last_successful_retrieve":"none"
},
"destination":{
"connection":"candlepin.company.com",
"status":"failure",
"message":"ConnectionRefusedError: [Errno 111] Connection refused",
"last_successful_send":"none",
"last_successful_send_job_status":"none"
}
}
] }